Problem

After ✔ 🎉 All 11 tasks completed successfully! appears, there was a noticeable long delay (sometimes several seconds) before terminal control returned to the user, slowing down the workflow.

Root Cause

The run command was starting iteration checkpoint commits asynchronously via the iterationEnd event handler without awaiting them. These git operations (invoking hooks, LFS, commit signing, auto-push) could continue running after the final success message was printed, keeping the Node.js event loop alive and delaying process.exit().

Solution

• Serialized checkpoint commits into a queue (checkpointQueue: Promise<void>) to
  eliminate concurrency issues
• Moved the flush point to immediately after await engine.start(activeTask)
  completes
• Now the CLI awaits all pending checkpoint work before stopping spinners and
  printing final output
• This ensures:
  • Checkpoints still complete (maintaining safety guarantees)
  • Process can exit immediately after success message
  • No visible delay to the user

Changes

Code

• src/commands/run.ts:
  • Added checkpointQueue promise chain for serialized checkpoint creation
  • Replaced fire-and-forget pattern with .then(async () => {...})
  • Added await checkpointQueue right after task completion to flush before final
    output

Documentation

• README.md → Troubleshooting section:
  • New entry: "Long delay before returning to prompt"
  • Explains that git hooks, LFS, commit signing, and auto-push can add latency
  • Lists mitigations:
• Disable checkpoints: autoCommit: false
• Disable auto-push: autoPush: false / pushStrategy: manual
• Inspect/disable slow hooks in .git/hooks/

Version

• Bumped package.json version from 0.1.4 → 0.1.5
• Added JOURNAL entry documenting the change

Testing

✅ All 311 tests pass
✅ Linting passes
✅ TypeScript compilation successful
✅ Build successful

Impact

• Behavioral: Users now see immediate control return after completion
• Safety: No change—checkpoints still complete before exit
• Performance: Eliminates perceived delay without changing CLI behavior
• Breaking: None

Related Issue

Resolves long delays reported when running multi-task workflows with git-intensive environments (Husky hooks, LFS, commit signing enabled).